In this case, the production folder can be used without change, if you took care to check the webGL export options when producing your 3MX scene.

It should be sufficient then to:

• Copy the production folder on the server, at the appropriate location (next to your webpage index.html file, for example)
• Access the application by going to your_site/your_production_folder_path/App
• If the page cannot be accessed, it might be necessary for you to change the access rights for your_production_folder

The case described above is the simplest use-case, but it also results in the webGL application being copied every time you create a new production.

Alternatively, you can use the same webGL application for all your productions. It is sufficient to change its configuration options, as described in the "Configuring the web viewer" section.

In both cases, the setup should be very similar to your local server setup, if you chose to use one. It is sufficient to copy your data from the local to the remote server, in the same format.

Just remember that the config.json file in your application has to contain relative, and not absolute paths. In other words, scene paths like this: "../Scene/Production.3mx" will work for both the local and remote server. But scene paths like this: "localhost/Scene/Production.3mx" will only work for the localhost.